{{ crumb }}
{{ pageTitle }}
Demo data Your roadmap

{{ ck.greeting }}

{{ ck.sub }}

Portfolio by stage
{{ b.name }} {{ b.n }}
Needs attention{{ ck.needsCount }}
Nothing is waiting on anyone right now.
Recent activity
30-day lighthouse project

{{ lh.title }}

{{ lh.outcome }}

Catalog case {{ lh.caseId }} ↗
Day {{ lh.day }} / 30{{ lh.range }}
UnderstandBuildPilotProve
{{ lh.doneLine }}
WEEK {{ w.n }} · {{ w.range }}{{ w.count }}
{{ w.phase }}
This week
Day-30 measuresBaseline in week 1, after in week 4, same method both times.
MeasureBaselineAfter {{ m.name }}
IDOpportunityStageWaveCapacityNext action · ownerSource
No opportunities match.
{{ rc.id }} {{ rc.stage }} {{ rc.wave }} {{ rc.source }} {{ rc.reqLine }}

{{ rc.title }}

{{ rc.dept }}Owner: {{ rc.owner }}Reported by {{ rc.reportedBy }}Catalog case {{ rc.caseId }} ↗
{{ s.name }}
{{ rc.signal }}
Stage gate · {{ rc.stage }} → {{ rc.nextStage }}
{{ ap.line }}
{{ a.label }}{{ a.status }}
{{ a.detail }}
The problemReported

{{ rc.problem }}

Why it is on the roadmap: {{ rc.why }}
Next: {{ rc.next }}{{ rc.nextOwner }}
How it gets automated
{{ s.n }}{{ s.level }}
{{ s.label }} {{ s.tag }}
Systems: {{ rc.systems }}
Benefits
{{ b.type }} · forecast
{{ b.forecast }}
{{ b.fL }}
{{ b.type }} · realized
{{ b.realized }}
{{ b.rL }}

{{ b.basis }}
Decisions on this record

None yet. Accept an assistant proposal or record a decision packet outcome.
{{ d.text }}{{ d.kind }} {{ d.byLine }}
Discussion
{{ c.ini }}
{{ c.who }}{{ c.role }}{{ c.when }}
{{ c.text }}
Notify
Pilot issues{{ ex2.openCount }} open
{{ e.text }}{{ e.meta }}
People and change readiness{{ chg.pct }}

{{ chg.affected }}

Activity
{{ a.when }}{{ a.who }} · {{ a.text }}
Assistant

It proposes. You decide, and your name goes on the record.

{{ as.answer }}
AI proposed · {{ p.kind }}{{ p.owner }}
{{ p.text }} {{ p.rationale }}
Choose a record
Pick a record to draft its decision packet.
{{ pk.id }}

{{ pk.title }}

The assistant drafts a one-page packet from this record and its catalog case: the decision requested, options, risks and measures. Benefit figures come straight from the record with their evidence stage.
Decision packet · {{ pk.id }}

{{ pk.title }}

Decision requested
{{ pk.p.ask }}

{{ pk.p.summary }}

The problem

{{ pk.p.problem }}

How it gets automated
  • {{ a }}
Benefits, with how each figure is known
{{ b.type }}{{ b.forecast }}{{ b.fL }}·{{ b.realized }}{{ b.rL }}

Unlike benefit types are never summed. Capacity stays in hours.

Options
{{ o.name }}
{{ o.what }}
{{ o.tradeoff }}
Risks and mitigations
{{ k.risk }}
{{ k.mitigation }}
How we will know it worked
  • {{ m }}
Recommendation
{{ pk.p.recommendation }}
{{ pk.decisionLine }}
Record the decision

Drafted by the assistant from the record. The decision is recorded by a person, by name.

Forecasts start as estimates. A figure becomes measured when you record it with the same method as the baseline, and finance-confirmed only when finance signs it off. Hours stay hours; unlike benefit types are never added together.

{{ t.label }}{{ t.value }} hrs/month{{ t.evL }}
Opportunity · capacityForecastForecast vs realizedRecord realizedEvidence
{{ r.forecast }}{{ r.fL }} {{ r.realized }} · {{ r.rL }}by {{ r.confirmedBy }}
{{ k.label }}{{ k.value }} {{ k.unit }}{{ k.sub }}
Weekly status summary
Drafted by the assistant from this week's tasks, stages and decisions.
Generate this week's summary to share with your sponsor or board.
{{ ex.w.headline }}
What moved
  • {{ x }}
Risks
  • {{ x }}
Decisions for you
  • {{ x }}
Next week
  • {{ x }}
Email it
Decisions made

No decisions recorded yet.
{{ d.text }}{{ d.meta }}
Roadmap
{{ w.name }}
{{ l.code }}{{ l.name }}

{{ l.what }}

Gates: {{ l.gates }}
{{ s.label }}{{ s.reqNote }}

Raising a level needs its gates checked and a named person. Every change lands on the record.
{{ l.name }}
{{ d.name }}{{ d.n }}
Quick wins
Big bets
Fill-ins
Reconsider
Effort → Value →

Value weighs the capacity forecast and how many people reported the problem. Effort comes from the catalog case. Both are estimates to guide the conversation.
Plain language · about a minute

What keeps going wrong?

No business case needed. Say who does the work, what they wait for and how often. The assistant drafts the record; you check it before it goes in.

AI proposed · draft recordCheck it, then create it.
Department
{{ sb.d.dept }}
Who does it
{{ sb.who2 }}
How often
{{ sb.freq }}
Benefit type
{{ sb.d.benefitType }}
The problem

{{ sb.d.problem }}

Closest catalog case: {{ sb.caseTitle }}. {{ sb.d.why }}{{ sb.d.caseId }} ↗
First questions
  • {{ q }}
Reported at MAXX
{{ hm.eyebrow }}

{{ hm.greeting }}

{{ hm.purpose }}

Your inbox{{ unreadCount }} unread
You are all caught up.
{{ c.title }}
{{ c.emptyText }}

New problems from staff, MAXX and the intake form. Match each one to a catalog case, merge duplicates, schedule it into a wave, or decline it with a reason. The person who reported it sees every outcome.

Nothing is waiting for triage.
{{ t.id }}{{ t.source }}{{ t.meta }}{{ t.signal }}

{{ t.problem }}

{{ t.matchLabel }} ↗
Closed
{{ c.title }}{{ c.why }}

Automations that are running in pilot or live. Anyone accountable can pause one; the reason goes on the record and everyone involved is told.

Sample data
Nothing is running yet.

{{ op.emptyText }}
{{ o.stage }}{{ o.status }}
{{ o.pausedLine }}
{{ m.label }}
{{ m.value }}
Last 7 days

{{ dlg.title }}

{{ dlg.body }}

Recorded as {{ meName }} · {{ today }}
{{ toast }}
View the Hub as
Each person sees their own work, inbox and permissions.
Inbox
For {{ meName }} · {{ roleLabel }}
You are all caught up.
ESC
{{ g.label }}
Nothing matches. Try a record ID, a department or a catalog case.